Using persistent memory technology as a host-side storage tier for clustered/distributed file systems, managed by host-side tier

ABSTRACT

Embodiments are described for a multi-node file system, such as a clustered or distributed file system, with a file system buffer cache and an additional host-side tier non-volatile storage cache such as 3DXP storage. Cache coherency can be maintained by one of three models: (i) host-side tier management, (ii) file system management, or (iii) storage array management. performing a storage tier-specific file system action in a file system that comprises a namespace that spans multiple tiers of storage.

TECHNICAL FIELD

This disclosure relates to the field of cache systems forclustered/distributed file systems.

BACKGROUND

A clustered file system is a file system which is shared by beingsimultaneously mounted on multiple servers or “nodes.” Clustered filesystems can provide features such as location-independent addressing andredundancy which improve reliability or reduce the complexity of otherparts of the clustered file system. A distributed file system is similarto a clustered file system, but a distributed file system does not shareblock level access with other nodes of the file system. Both clusteredand distributed file systems (collectively, and individually“clustered/distributed file systems”, or “C/DFS”) gain a performancebenefit by caching reads and writes to physical storage units attachedto nodes of the C/DFS. In any caching system, cache coherency must bemaintained. Cache coherency ensures that a file system read operationalways returns the most recent version of a file system object. Cachecoherency also ensures that a write operation writes the most recentversion of a file system object to storage. When a C/DFS node reads acache, peer nodes in the C/DFS must be notified to ensure that they areaccessing the most recent version of a file system object or objectextent. When a C/DFS node writes to cache, peer nodes must be notifiedto invalidate older cached versions of file system objects.

Currently, caching is performed using volatile random access memory(VRAM). Read/write access to VRAM is fast, but VRAM is expensive interms of cost. In a C/DFS system, the cost of cache is multiplied by thenumber of nodes in the C/DFS. Thus, a C/DFS must balance the cost ofVRAM cache against the performance gain offered by caching storage readsand writes. In addition, volatile RAM cache is vulnerable to data lossdue to power outages and unexpected, uncontrolled C/DFS node failures.

New, fast, non-volatile random access memory (“persistent cache”)storage technologies, such as 3D Crosspoint (3DXP) are coming on themarket that have similar read/write access times to VRAM and are lessexpensive than VRAM and have access times that are similar to VRAM. 3DXpoint (3DXP) is a non-volatile memory technology by Intel® and MicronTechnology®, that is a bit storage based on a change of bulk resistance,in conjunction with a stackable cross-gridded data access array. A C/DFSwould benefit from the fast access time, non-volatility, and lower costof these new storage technologies. A challenge with providing apersistent cache tier below a VRAM file buffer cache in a C/DFS is thatthe persistent cache does not participate in the C/DFS cache coherencyprotocol for the VRAM file buffer cache. When a peer node of a C/DFSreceives cache invalidations for shared file system objects, the C/DFSwill not know that the persistent cache may contain an invalid versionof the file system object. Conversely, when a peer node of a C/DFSreceives a request to flush writes from its VRAM file buffer cache tothe C/DFS, the writes may be held in the persistent cache for some timeafterwards, causing the peer nodes to believe that the most recentversion of a file system object (or object extent) is persisted at aphysical storage device in (e.g. at a storage array) when in fact thewrite is only contained with the persistent storage buffer visible tothe node of the C/DFS that initiated the cache flush operation.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings inwhich like reference numerals refer to similar elements.

FIGS. 1A and 1B illustrate, in block diagram form, components andfunctionality of a clustered/distributed file system (C/DFS) whereineach node in the C/DFS has a file system buffer cache and a host-sidecache with host-side cache coherency managed by a host-side cachecoherency management system, independent from the file system buffercache, in accordance with some embodiments.

FIGS. 2A and 2B illustrate, in block diagram form, components andfunctionality of a clustered/distributed file system (C/DFS) whereineach node in the C/DFS has a file system buffer cache and a host-sidecache with file system buffer cache coherency and host-side cachecoherency managed by a file system management system, in accordance withsome embodiments.

FIGS. 3A and 3B illustrate, in block diagram form, components andfunctionality of a clustered/distributed file system (C/DFS) whereineach node in the C/DFS has a file system buffer cache and a host-sidecache with the host-side cache coherency managed by cache coherencylogic in a storage device, in accordance with some embodiments.

FIG. 4 illustrates, in block diagram form, a method of file systembuffer cache and host-side cache coherency management in aclustered/distributed file system (C/DFS), managed by a host-side tiercache coherency logic, in accordance with some embodiments.

FIG. 5 illustrates, in block diagram form, a method of file systembuffer cache and host-side cache coherency management in aclustered/distributed file system (C/DFS), managed by a file systemcache coherency logic, in accordance with some embodiments.

FIG. 6 illustrates, in block diagram form, a method of file systembuffer cache and host-side cache coherency management in aclustered/distributed file system (C/DFS), managed by a cache coherencylogic in a storage device processing system, in accordance with someembodiments.

FIG. 7 illustrates an exemplary embodiment of a software stack usable insome embodiments of the invention.

FIG. 8 illustrates, in block diagram form, an exemplary computing systemfor implementing concepts described herein.

DETAILED DESCRIPTION

In the following detailed description of embodiments, reference is madeto the accompanying drawings in which like references indicate similarelements, and in which is shown by way of illustration manners in whichspecific embodiments may be practiced. These embodiments are describedin sufficient detail to enable those skilled in the art to practice theinvention, and it is to be understood that other embodiments may beutilized and that logical, mechanical, electrical, functional and otherchanges may be made without departing from the scope of the presentdisclosure. The following detailed description is, therefore, not to betaken in a limiting sense, and the scope of the present invention isdefined only by the appended claims.

Embodiments are described for managing a host-side tier cache of eachnode of a clustered/distributed file system (C/DFS). Each node in thefile system can have both a file system buffer cache, which is typicallya volatile random access memory (RAM), and a host-side tier cache, whichcan be a non-volatile high-speed memory. Three different embodiments aredescribed for managing cache coherency in the nodes of the C/DFS: (i) ahost-side tier managed embodiment, (ii) a file system managedembodiment, and (iii) a storage device managed embodiment. The describedembodiments can be implemented as a “snoop” type, write-back cachecoherency model, wherein nodes communicate with one another to managecoherency of the caches. Other cache coherency protocols can beimplemented using the systems and methods described herein.

In a first embodiment, in response to receiving, by a host-cache on afirst node of a multi-node file system (e.g. C/DFS), a copy of a filesystem object (FSO) from a file system buffer cache on the first node,the following operations can be performed. The FSO can be stored in ahost-side cache of the first node in the multi-node file system.Host-side cache coherency logic can send a message to a second and athird node of the multi-node file system to invalidate a copy of the FSOin a host-side cache of each of the second and third nodes. A copy ofthe FSO from the host-side cache of the first node can be sent to ahost-side cache of at least the second node of the multi-node filesystem, thereby updating the host-side cache of the second node tocontain the most recent version of the FSO. The host-side cache of eachof the first, second, and third nodes can comprises a non-volatilestorage, distinct from the file system buffer cache, and distinct from abulk storage device, such as a disk drive or storage array. Cachecoherency logic of the host-side cache of the nodes in the multi-nodefile system can be independent of cache coherency logic of the filesystem buffer cache on each of the nodes in the multi-node file system.In an embodiment, sending of the copy of the FSO from the host-sidecache of the first node to the host-side cache of the second node can bein response to a request from the second node. Flushing the receivedcopy of the FSO from the host-side cache of the first node to a storagesystem can be in response to an event. In an embodiment, the event canbe one of receipt message to the FSO from the host-side cache, the FSOhas not been read for a predetermined period of time, storage availablein the host-side cache of the first node is below a threshold minimumvalue, or receipt of a request to flush pending writes has been receivedfrom the storage system. In an embodiment, each of the first, second,and third nodes can include host-side cache coherency logic, and thehost-side cache coherency logic of the first, second, and third nodescan communicate with each other to implement coherency logic for thecombined first, second, and third node host-side caches.

In a second embodiment, in response to receiving, by a file system of afirst node in a multi-node file system, a request to read a file systemobject (FSO), the following operations can be performed. A message canbe sent to a file system of each of a plurality of other nodes in themulti-node file system, indicating an intent to read the FSO. Theintent-to-read message sent to each file system of a plurality of othernodes in the multi-node file system can cause the file system of thenode with the most recent version of the FSO to flush its copy of theFSO to a storage device. The file system of the first node can read theFSO from the storage device and store the FSO in a host-side cache ofthe first node. A copy of the FSO from the host-side cache of the firstnode, can be provided to fulfill the request. In an embodiment, the copyof the FSO from the host-side cache is provided via a file system buffercache of the first node. In an embodiment, the host-side cache cancomprise a non-volatile storage, distinct from the file system buffercache and distinct from a bulk storage device such as a disk drive orstorage array. In an embodiment, the operations can further includenotifying the file system of each node in the plurality of nodes in themulti-node file system when the most recent version of the FSO has beenflushed to the storage device. Operations can further includedetermining the node in the multi-node file system that has the mostrecent version of the FSO, and causing the determined node to flush thecopy of the FSO from a file system buffer cache of the determined nodeto a host-side cache of the determined node. In an embodiment,operations can further include flushing the copy of the FSO in thedetermined node from the host-side cache of the determined node to thestorage device. In an embodiment, the cache coherency logic in each nodecan manage both the file system buffer cache of the node and thehost-side cache of the node.

In a third embodiment, the host-side cache buffer of each node of aplurality of nodes in a multi-node file system (e.g. C/DFS) can bemanaged by processing logic in a storage device of the multi-node filesystem, including the following operations. A storage device in amulti-node file system can receive an indication of a read request for acopy of a file system object (FSO) at a second node of the multi-nodefile system. The storage device can also receive an indication that ahost-side cache of a first node within the multi-node file systemcontains the most recent version of the FSO as among a plurality ofnodes of the multi-node file system. The storage device can instruct thehost-side cache of the first node to write the FSO to the storagedevice. In an embodiment, the coherency of a host-side cache of eachnode in the multi-node file system can be managed by the storage device.In an embodiment, the host-side cache of each node in the multi-nodefile system is distinct from a file system buffer cache of each node ofthe multi-node file system. In an embodiment, operations can furtherinclude the storage device sending an invalidate FSO message to the eachof the plurality of nodes of the multi-node file system, other than thefirst node. Operations can also include the storage device sending thecopy of the FSO received from the host-side cache of the first node tothe host-side cache of the second node. In an embodiment, in response tothe storage device receiving a read request for the FSO from a thirdnode, before receiving an indication of invalidation of the FSO,operations can further include instructing the host-side cache of thefirst node or the second node to move a copy of the FSO to the host-sidecache of the third node.

Any of the above methods can be embodied on a non-transitorycomputer-readable medium programmed with executable instructions that,when executed, perform the method. A system can be programmed withexecutable instructions that, when executed by a processing system thatincludes at least one hardware processor, can perform any of the abovemethods.

Some embodiments include one or more application programming interfaces(APIs) in an environment with calling program code interacting withother program code being called through the one or more interfaces.Various function calls, messages or other types of invocations, whichfurther may include various kinds of parameters, can be transferred viathe APIs between the calling program and the code being called. Inaddition, an API may provide the calling program code the ability to usedata types or classes defined in the API and implemented in the calledprogram code. At least certain embodiments include an environment with acalling software component interacting with a called software componentthrough an API. A method for operating through an API in thisenvironment includes transferring one or more function calls, messages,or other types of invocations or parameters via the API.

FIGS. 1A and 1B illustrate, in block diagram form, components andfunctionality of multi-node file system, such as a clustered/distributedfile system (C/DFS) 100, wherein each node 110 in the C/DFS has a filesystem buffer cache 125 and a host-side cache 150 with host-side cachecoherency managed by a host-side cache coherency management system, inaccordance with some embodiments. Method 400, described below withreference to FIG. 4, describes a method ensuring cache coherency logicin accordance with FIGS. 1A and 1B.

In this embodiment, a host-side cache 150 and host-side cache coherencymanagement layer is introduced that coordinates synchronization ofwrites and write invalidations within the host-side cache 150. Thehost-side cache 150 can operate independently from theclustered/distributed file system (C/DFS) 100 and a storage device 250,such as a storage array, coupled to the C/DFS 100. When a write isissued by a file system of a node 110 of C/DFS file system 100, the filesystem of the node 110 notifies peer file system nodes 110 to invalidatetheir local file system buffer caches 125. These writes will eventuallybe flushed from the node's file system buffer cache 125 to the node'shost-side cache 150. At that time, coherency logic of the host-sidecache 150 for the node 110, issues an invalidation message host-sidecaches 150 of peer nodes 110 in the C/DFS 100, so that they willinvalidate any older versions of the same file system object (FSO) thatmay currently reside there. A read from any file system node 110 is anexample action that can cause the host-side cache 150 of any other node110 that currently holds an unwritten copy of the requested FSO in itsfile system buffer cache 125 to flush the copy of the FSO to the node'shost-side cache 150. This flush causes invalidations, similar to thewrite case. Once flushed, the requesting node's 110 host-side cache 150fetches a copy of the file system object from the peer node 110 that hasthe most recent copy of the file system object. In addition, file buffercache 125 (e.g. 125A) can periodically flush (FIG. 1A, (3)) a mostrecent version of FSO 130 (e.g, FSO 130A) from buffer cache 125 (e.g.,125A). Although buffer cache 125 need not be aware of host-side 150, HSTCoherency Mgt. 140 can detect flush messages from buffer cache 125,intended to flush to storage array 250, intercept those messages, andstore the flushed FSO 130 to host-side cache 150 (e.g. 150A) as FSO 155.Host-side cache 150 can, in turn, periodically and independently frombuffer cache 125, flush (FIG. 1A, (4)) a most recent version of FSO 155(e.g. FSO 155A) to storage array 250. For purposes of continuing withthe example that a flush from buffer cache 125 is initiated by a write(FIG. 1B, (1)) operation from application 115 (e.g. 115A), and fordescription of FIG. 1B, it is presumed that flush operation (FIG. 1B,(2)) from buffer cache 125 is in response to a read request (FIG. 1B,(1)).

A clustered/distributed file system (C/DFS) 100 can include a pluralityof file system nodes, such as cluster nodes 110A, 110B, and 110C. In thefollowing description, unless a specific node or element of a node isindicated, a cluster node and its elements are generically referencedwithout a subscript letter, e.g. cluster node 110, and elements of acluster node, e.g. application(s) 115, operating system 120, file buffercache 125, and host-side cache 160.

Each cluster node 110 can include one or more applications 115 and anoperating system 120. In the embodiments described in FIGS. 1A and 1B,operating system (OS) 120 can include drivers, application programminginterfaces (APIs) or other software that implements a file system,include a namespace for files, read/write functionality, mapping of filesystem data structures to one or more logical unit numbers (LUNs) of astorage device, interprocess and inter-node communications, file systembuffer cache logic, including coherency logic. Operating system 120 caninclude cache coherency logic, implemented as hardware, software, and/ora combination thereof, to maintain coherency of the file system buffercache 125, independently from host-side tier (HST) cache coherencymanagement 140 for host-side cache 150 for each node. File system buffercache 125 can be implemented as volatile random access memory (RAM).Host-side cache 150 can be implemented using high-speed non-volatile,persistent, memory that is distinct from storage array(s) 250. Host-sidecache 150 can be implemented using, for example, 3D Xpoint (3DXP), anon-volatile memory technology by Intel® and Micron Technology®, that isa bit storage based on a change of bulk resistance, in conjunction witha stackable cross-gridded data access array. Host-side cache 150 canalso be implemented using battery-backed RAM, flash memory, or otherhigh-speed non-volatile memory, new or existing. Host-side cache 150 cancomprise a write-back cache, supplemental to file system buffer cache125. In an embodiment, cache coherency logic for file system buffercache 125 and for HST coherency management 140 can be “snoop” type cachecoherency protocol.

Operating system (OS) 120 can include communication capabilities suchthat each node 110A . . . 110C can communicate via one or more calls tocommunication services of OS 120A . . . OS 120C. Communication can bevia a common bus or backplane, for nodes implemented inside a commonserver backplane. Inter-node 110 communication can be via high-speednetwork, such as network 200, shared memory, inter-processcommunication, or other communication methods. Network 200 can be anytype of network including Ethernet, Wireless, USB, Fire-Wire,Token-Ring, fiber-optic, high-speed interconnecting bus, Fibre Channel,or other type of network. C/DFS 100 can further include one or morestorage arrays 250, that expose a plurality of logical unit numbers(LUNs) of storage 260 to the nodes of C/DFS 100. A storage array can be,for example, an EMC® Data Domain® file system, or other storageappliance. A storage array can comprise a large plurality of storageunits, such as disk drives, interconnected with a high-speed backplaneor network, and can including processing logic, that may include one ormore hardware processors, memory, network interfaces, display(s), and anoperating system and drives to implement, e.g., the storage appliance ina Storage Area Network (SAN).

Operation of cache coherency for buffer cache 125 and host-side cache150 is shown by way of example in FIGS. 1A and 1B. Referring to FIG. 1A,the example includes writing (1) of a file system object (FSO) 130A byapplication 115A to a node file system implemented by Operating System(OS) 120A. Multiple copies of the FSO 130 can exist within the C/DFS100. For example, a read or write operation at node 110B can result inan existing copy of FSO 130B in buffer cache 125B and/or a copy of FSO155B in host-side cache 150B. Similarly, a copy of FSO 130C and/or FSO155C can exist in node 110C buffer cache 125B and/or host-side cache150C, respectively. In response to write (1) by application 115A,coherency logic in OS 120A can cause buffer cache 125A to send (2) an“invalidate copy of FSO 130” message to nodes 110B and 110C. Invalidatedcopies of FSO 130B and 130C are shown with hashed lines in FIG. 1A.

Referring now to FIG. 1B, a read request (1) from Application(s) 115Bfor a copy of FSO 130, or other operation that requires a most recentcopy of FSO 130, can be received by OS 120B at node 110B. Inter-nodecommunication among nodes 110A-110C and buffer cache coherency logic ofOS 120A-120C can determine that node 110A, buffer cache 125A, has themost recent copy of FSO 130 (FSO 130A). In response to receiving theread request (1), and the determination that buffer cache 125A has themost recent copy of FSO 130 (130A), buffer cache coherency logic of OS120B can issue a “flush copy of FSO 130” message to peer node 110A. Alsoin response to the read request (1) of FIG. 1B, and since node 110C doesnot contain the most recent copy of FSO 130, buffer cache coherencylogic of OS 120B can send an “invalidate copy of FSO 130 (FS 130C)” tonode 110C to invalidate the copy FSO 130C in buffer cache 125C.

HST coherency mgt. 140A-140C for host-side caches 150A-150C can be awareof coherency logic communications for buffer caches 125A-125C. Inresponse to the determination that node 110A buffer cache 125A has themost recent copy of FSO 130 (130A), HST Coherency Mgt 140A awareness ofthe flush (2) message sent from OS 120B to OS 120A, HST Coherency Mgt140A can cause host-side cache 150A to receive FSO 130A and store FSO130A in host-side cache 150A as FSO 155A. FSO 155A is the most recentcopy of FSO 155, as between host-side caches 150A-150C in nodes110A-110C, respectively.

In response to host-side cache 150A storing FSO 155A, HST Coherency Mgt.140A for node 110A can send (5) an “invalidate copy of FSO 150” messageto nodes 110B and 110C. At node 110B, HST Coherency Mgt. 140B thus marksFSO 150B as invalid, and at node 110C, HST Coherency Mgt. 140C marks FSO150C as invalid.

To satisfy the read request (1) at node 110B, by, e.g., application115B, HST Coherency Mgt. 140B can request (6) the most recent copy ofFSO 155 (155A) from host-side cache 150A. In response, HST CoherencyMgt. 140A can send (7) host-side cache 150A copy of FSO 155A tohost-side cache 150B. Thus, host-side cache 150B at node 110B now has acopy of the most recent copy of FSO 155 stored in host-side cache 150Bas FSO 155B.

Buffer cache coherency logic in OS 120B of node 110B can be aware thathost-side cache 150B now has a most recent copy of FSO 155 (155B) byvirtue of awareness of communications for cache coherency between nodesof the C/DFS 100. Buffer cache 125B can read (8) FSO 155B from host-sidecache 150B and store 150B in buffer cache 125B as FSO 130B. Similarly,OS 120B can read FSO 130B from buffer cache 125B and provide (9) FSO130B to requesting application 115B, thereby satisfying the initialrequest (1) by application(s) 115B for a most recent copy of FSO 130.

After the above processing, host-side cache 150A of node 110A andhost-side cache 150B of node 110B both hold a same, most recent copy ofFSO 155. HST Coherency Mgt. 140A and 140B can coordinate to determinewhich copy of FSO 155 (155A or 155B) will be written-back (10) tostorage array 250 as the most recent copy of FSO 130. Timing of thewrite-back of FSO 155A or FSO 155B to storage array 250 can beasynchronous with the above cache coherency logic, so long as FSO 155Aor 155B has not been invalidated by subsequent cache coherencyoperations. HST Coherency Mgt. 140A-140C can also coordinate to the mostrecent version of a modified FSO 155 to storage array 250 independentfrom a read or write operation by, e.g. an application 115. This mayoccur, for example, during periods of low activity in order to avoidhaving to flush synchronously during the read request.

FIGS. 2A and 2B illustrate, in block diagram form, components andfunctionality of a clustered/distributed file system (C/DFS) 100 whereineach node 110 in the C/DFS 100 has a file system buffer cache 125 and ahost-side cache 150 with file system buffer cache coherency andhost-side cache coherency managed by a file system management system ofa node 110, in accordance with some embodiments. Method 500, describedbelow with reference to FIG. 5, describes a method having the cachecoherency logic described below with reference to FIGS. 2A and 2B.

In the embodiment of FIGS. 2A and 2B, the Clustered/Distributed filesystem 100 cache coherency protocol is extended to include awareness ofthe host-side tier 150. This embodiment introduces a new messagingmechanism that includes a flush and an invalidation message originatingfrom each node 110 of the multi-node file system 100 to the host-sidecache 150 of each node 110 in the multi-node file system 100. When awrite is issued by a node 110 of the multi-node file system 100, thenode 110 first sends file system buffer cache 125 invalidation messagesto other file system nodes 110. These messages may, in turn, issueinvalidate messages to the local host-side cache 150 of each node 110,to invalidate any local copies of the file system object (FSO) beingwritten by the write originating at a node 110. For a read operation,the file system node 110 that originates the read operation notifies theother nodes 110 of the multi-node file system 100 of the originatingnode's 110 intent to read the file system object. This causes the otherfile system nodes 110 to flush any pending writes to that same filesystem object from their respective file system buffer caches 125 totheir respective host-side caches 150. Once each node 110 has flushedits copy of the FSO from file system buffer cache 125 to the host-sidecache 150 of the node, the node's file system will issue the new flushmessage to the host-side cache 150 to flush the copy of the FSO that isin the host-side cache 150 of the node, to the storage array 250. Thenthe read operation continues on the originating node 110 and the FSO isread from the storage array 250 into the local host-side cache 150 ofthe originating node 110.

Cluster nodes 110A-110C and application(s) 115A-115C, buffer cache125A-125C, and host-side cache 150A-150C have been described above withreference to FIGS. 1A and 1B. For brevity, these elements will not bedescribed again here.

In the embodiment described with reference to FIGS. 2A and 2B, operatingsystems 120A-120C can include cache coherency logic that is aware ofboth the file system buffer cache 125 and the host-side buffer cache 150of each node. Communication of cache coherency messages between OS120A-120C can be shared internally on each node 110 to implement cachecoherency for both file system buffer cache 125 and host-side cache 150for cluster nodes 110A-110C.

Operation of cache coherency for buffer cache 125 and host-side cache150 is shown by way of example in FIGS. 2A and 2B. Beginning with FIG.2A, the example includes writing (1) of a file system object (FSO) 130Aby application 115A. Multiple copies of the FSO 130 can exist within theC/DFS 100. For example, a read or write operation at node 110B can causea copy of FSO 130B to exist in buffer cache 125B and/or a copy of FSO155B to exist in host-side cache 150B. Similarly, a copy of FSO 130Cand/or FSO 155C can exist in node 110C buffer cache 125B and/orhost-side cache 150C, respectively.

In response to the write (1) by application 115A, cache coherency logicin OS 120A can cause buffer cache 125A to send (2) an “invalidate copyof FSO 130” message to nodes 110B and 110C. Cache coherency logic in OS120B can invalidate copy of FSO 130 (FSO 130B) in cache 125B. Cachecoherency logic in OS 120C can similarly invalidate a copy of FSO 130(FSO 130C) in cache 125C. Invalidated copies of FSO 130B and 130C areshown with hashed lines in FIG. 2A. Cluster node 110B host-side cache150B may already have a copy of FSO 130, stored as host-side cache FSO155B. In response to OS 120B receiving (2) the “invalidate file buffercache 125 copy of FSO” message from node 110A, file buffer cachecoherency logic in OS 120B can send (3) an “invalidate copy of FSO 130(referenced as 155B)” message to host-side cache 150B. Similarly, inresponse to OS 120C receiving (2) the “invalidate file buffer cache 125copy of FSO” message from node 110A, file buffer cache coherency logicin OS 120C can send (3) an “invalidate copy of FSO 130 (referenced as155C)” message to host-side cache 150C. FSO 155B and FSO 155C areinvalidated, accordingly.

Continuing to FIG. 2B, a C/DFS 100 node, e.g. cluster node 110B, cangenerate a request (1) for a copy of FSO 130, such as from application115B. Cache coherency logic in OS 120B of node 110B can send (2) an“intent to read a copy of FSO 130” message to each of nodes 110A and110C. It can be seen from FIG. 2A, that buffer cache 125A previouslyreceived a write operation and therefore contains the most recent copyof FSO 130 (FSO 130A). It can also be seen from FIG. 2A that buffercache 125C received an “invalidate copy of FSO 130” message. Thus, thecopy of FSO 130 in buffer cache 125A is the most recent copy of FSO 130,and the copy of FSO 130 in buffer cache 125C is invalid. Accordingly,when OS 120A of node 110A receives the “intent to read a copy of FSO130” message from OS 120B, the message (2) triggers an operation (3) atcluster node 110A to flush FSO 130A from buffer cache 125A to host-sidecache 150A. No such action is triggered on node 110C, because the copyof FSO 130 at node 110C is invalid. The resulting copy of FSO 130A thatis stored in host-side cache 150A is referenced as FSO 155A. Cachecoherency logic in OS 120A can further (4) flush the FSO 155A to storagearray(s) 250. In an embodiment, storage array(s) 250 can return a writeacknowledgement to node 110A in response to flushing FSO 155A to storagearray(s) 250. In an embodiment, cache coherency logic in OS 120A canthen send a message to nodes 110B and 110C that FSO 155A (a most recentcopy of FSO 130) confirming that the most recent version of FSO 130(155A) has been written to storage array(s) 250 and the write has beenacknowledged by the storage array(s) 250 as being complete.

Upon receiving the notification from node 110A that FSO 155A has beenwritten to storage device 250, cache coherency logic in OS 120B can thencause host-side cache 150B to (5) read FSO 130 from the storage array250 and store FSO 130 into host-side cache 150B. The FSO 130 read fromstorage is indicated as FSO 155B in host-side cache 150B of node 110B.Cache coherency logic in OS 120B can further read (6) FSO 155B fromhost-side cache 150B and store the FSO in buffer cache 125B as FSO 130B.Buffer cache 125B can then provide (7) FSO 130B to requestingapplication 115B as the most recent version of FSO 130. Cache coherencylogic in OS 120A-OS 120C can also periodically initiate a “flush”message to a host-side cache 150A-150C for a modified FSO 155independent from a read or write operation by, e.g. an application 115.This may occur, for example, during periods of low activity in order toavoid having to flush synchronously during the read request.

FIGS. 3A and 3B illustrate, in block diagram form, components andfunctionality of a clustered/distributed file system (C/DFS) 100 whereineach node in the C/DFS 100 has a file system buffer cache 125 and ahost-side cache 150 with host-side cache coherency managed by a storagedevice 250, in accordance with some embodiments. Method 600, describedbelow with reference to FIG. 6, describes a method having the cachecoherency logic described below, with reference to FIGS. 3A and 3B.

In this embodiment, the storage array 250 contains host-side cachecoherency logic 270 that manages host-side cache coherency. HSTcoherency mgt. 270 in storage array 250 can be implemented by hardwareand/or software of processing system 265 of storage array 250.Processing system 265 can include one or more hardware processors,memory, high-speed buses, an operating system, and other processingelements to implement storage array 250 management, including HSTCoherency Mgt. 270. Exemplary hardware is described below with referenceto FIG. 8. In this embodiment, file system objects (FSO) are movedbetween the storage array 250 and the host-side caches 150, similar toany other storage tier. When the storage array 250 decides that it wouldbe beneficial to place a file system object on a specific node's 110host-side cache 125, it will do so. The storage array 250 can alsodecide to move an FSO from a node 110 back to the storage array 250, orto another node 110. When the file system of a node 110 issues a write,it proceeds as normal for the clustered/distributed file system 100.Eventually, the write will be flushed from the file system buffer cache125 and stored in the local host-side cache 150. When a read occurs, thenode 110 originating the read will signal to its peer nodes 110 to flushtheir buffer caches 125, again as normal for the file system of a node110. When a buffer cache 125 FSO is flushed to the host-side cache 150,the host-side cache 150 and the storage array 250 can determine if thatFSO should be flushed all the way to the storage array 250. Thishappens, for example, when a read occurs at one node 110 while a peernode 110 has yet to flush the latest version of the file system objectto the storage array 250 from its host-side cache 150. Once the FSO hasbeen flushed all the way to the storage array 250, the requesting node110 can continue with the read.

Cluster nodes 110A-110C and application(s) 115A-115C, buffer cache125A-125C, and host-side cache 150A-150C have been described above withreference to FIGS. 1A and 1B. For brevity, these elements will not bedescribed again here.

In the embodiment described with reference to FIGS. 3A and 3B, operatingsystems (OS) 120A-120C can include cache coherency logic that managesthe buffer cache 125. In an embodiment, cache coherency logic of OS120A-120C can communicate with both the file system buffer cache 125 andthe host-side buffer cache 150 of each node 110 of the C/DFS 100.Storage array 250 further includes a host-side coherency management 270logic that can determine when to move a file system object (FSO) to, orfrom, the storage array 250. Communication of cache coherency messagesbetween OS 120A-120C can be shared internally on each node 110 toimplement cache coherency for both file system buffer cache 125 andhost-side cache 150 for cluster nodes 110A-110C. Communication of cachecoherency logic between storage array HST coherency mgt. 270 and cachecoherency logic in OS 120A-120C can cross storage area network (SAN)200.

Operation of cache coherency for buffer cache 125 and host-side cache150 is shown by way of example in FIGS. 3A and 3B. Beginning with FIG.3A, the example includes writing (1) of a file system object (FSO) 130Aby application 115A. Multiple copies of the FSO 130 can exist within theC/DFS 100. For example, a read or write operation at node 110B can causea copy of FSO 130B to exist in buffer cache 125B and/or a copy of FSO155B to exist in host-side cache 150B. Similarly, a copy of FSO 130Cand/or FSO 155C can exist in node 110C buffer cache 125B and/orhost-side cache 150C, respectively.

In response to the write (1) by application 115A, cache coherency logicin OS 120A can cause buffer cache 125A to send (2) an “invalidate copyof FSO 130” message to nodes 110B and 110C. Cache coherency logic in OS120B can invalidate the copy of FSO 130 (FSO 130B) in cache 125B. Cachecoherency logic in OS 120C can similarly invalidate the copy of FSO 130(FSO 130C) in cache 125C. Invalidated copies of FSO 130B and 130C areshown with hashed lines in FIG. 3A. Cluster node 110B host-side cache150B may already have a copy of FSO 130, stored as host-side cache FSO155B. Cluster node 110C host-side cache 150C may already have a copy ofFSO 130, stored as host-side cache FSO 155C.

Continuing to FIG. 3B, a C/DFS 100 node, e.g. cluster node 110B, cangenerate a request (1) for a copy of FSO 130, such as from application115B. In response to the read (1) request at OS 120B, cache coherencylogic in OS 120B can (2) send a “flush FSO 130” message each of nodes110A and 110C. Nodes 110A-110C can each (3) flush their respective copyof FSO 130 from their file buffer caches 125A-125C to their respectivehost-side caches 150A-150C. HST Coherency Mgt. 270 in storage array 250can monitor host-side caches 150A-150C to determine when a host-sidecache 150 read or write operation has been performed. Thus, HOSTCoherency Mgt. 270 can determine which of FSO 155A-155C is the mostrecent copy of the FSO 130 stored in a host-side cache 150 of a clusternode 110 of C/DFS 100. Based on the determination that FSO 155A is themost recent copy of the FSO 130, HST Coherency Mgt. 270 can (4) instructhost-side cache 150A to write FSO 155A to storage array 250. Host cache150A then (5) writes the FSO 155A to storage array 250 as instructed byHST Coherency Mgt. 270 of storage array 250. Since coherency ofhost-side caches 150A-150C is managed by HST Coherency Mgt. 270 instorage array 250, storage array 250 need not send a writeacknowledgement to host-side cache 150A that FSO 155A was successfullywritten. Instead, when HST Coherency Mgt. 270 determines that the writeof FSO 155A to storage array 250 is complete, HST Coherency Mgt. 270 cansend (6) a “invalidate FSO 155” message to host-side cache 150B and150C. In an embodiment, HST Coherency Mgt. 270 need not send (6) an“invalidate FSO 155” message to host-side cache 150A, because HSTCoherency Mgt. 270 knows that FSO 155A is the most recent copy of FSO155 as between the host-side caches 150A-150C. HST Coherency Mgt. 270can send an instruction to node 110B to (7) read the most recent copy ofFSO 130 from storage array 250 and store the FSO into host-side cache150B. Coherency logic on OS 120B can detect the write of FSO 130 tohost-side cache 155B, and then (8) read FSO 155B from host-side cache150B and store the FSO in buffer cache 125B as FSO 130B. OS 120B canthen provide (9) the FSO 130B to requesting application 115B in responseto the initial read request (1) by application 115B. In addition, thestorage array 250 can periodically initiate a “flush” message to thehost-side cache 150A-150C independent from a read or write request from,e.g., an application 115. This may occur, for example, during periods oflow activity in order to avoid having to flush synchronously during theread request.

FIG. 4 illustrates, in block diagram form, a method 400 of file systembuffer cache and host-side cache coherency management in aclustered/distributed file system (C/DFS), managed by a host-side tiercache coherency logic, in accordance with some embodiments. Structureand logic for implementing method 400 is described above with referenceto FIGS. 1A and 1B.

In operation 405, a first node (N1) in a multi-node file system (MNFS)can receive a “write file system object (FSO),” instruction to write amost recent copy of an FSO, such as FSO 130 of FIG. 1A. The writeoperation may result in the FSO being written to one or more caches, asdistinguished from writing directly to a storage device.

In operation 410, cache coherency logic in, e.g. an operating system120, can send an “invalidate copy of FSO” message an operating system ofeach of a second node (N2) and a third node (N3) to copies of the FSO inthe buffer cache 125 of each of N2 and N3.

In operation 415, node N2 can invalidate a copy of the FSO in its buffercache, if such a copy of the FSO exists. Similarly, N3 can invalidate acopy of the FSO in its buffer cache, if such as a copy of the FSOexists.

In operation 420, either of N2 or N3 (in this example, N2) can receive a“read FSO” request to read a most recent copy of the FSO. The readrequest asks for the most recent copy of the FSO, and, in an embodiment,the read request does not need to specify a source node, cache, orstorage from where the copy of the FSO is read.

In operation 425, nodes N1-N3 can use inter-node communication todetermine which of nodes N1-N3 has a most recent copy of the FSO in abuffer cache. In the example of method 400, node N1 buffer cache has themost recent copy of the FSO, due to the “write FSO” instruction receivedat node N1 in operation 405, above.

In operation 430, buffer cache coherency logic in OS 120 can send amessage from N2 to N1 for N1 to flush buffer cache copy of the FSO. Inthis embodiment of FIGS. 1A, 1B, and method 400, buffer cache coherencylogic in OS 120 need not be aware that N1 flushing its copy of the FSOresults in flushing the copy of the FSO to a host-side cache of N1.

In operation 435, buffer cache coherency logic of N2 can send an“invalidate copy of FSO” to buffer cache coherency logic of node N3. Inan embodiment, buffer cache coherency logic of N2 can invalidate N2buffer cache copy of the FSO, since it was been determined that the mostrecent copy of the FSO is in N1 buffer cache, in operation 425, above.

In operation 440, buffer cache N1 can flush its copy of FSO to host-sidecache of node N1. In an embodiment, N1 buffer cache coherency logicissues a generic “flush” command on its buffer cache, and host-side tiercoherency logic for N1 can intercept the flush command to cause the N1buffer cache copy of the FSO to be flushed to the N1 host-side cache.

In operation 445, host-side cache coherency logic for N1 can send an“invalidate host-side cache copy of FSO” message just to nodes N2 andN3, since N1 host-side cache has the most recent host-side cache copy ofthe FSO, as between nodes N1-N3.

In operation 450, it can be determined that N1 host-side cache has themost recent copy of the FSO as between the host-side caches of nodesN1-N3.

In operation 455, N1 host side cache can receive a “request for copy ofFSO” message from N2 host-side cache coherency logic.

In operation 460, N1 host-side cache coherency logic can send the mostrecent copy of the FSO to N2 host-side cache.

In operation 465, node N2 host-side coherency logic can send the mostrecent copy of FSO, stored in N2 host-side cache, to N2's file buffercache.

In operation 470, node N2 file buffer cache can provide its copy of theFSO to, e.g., requesting Application(s) 115B to satisfy the request forthe most recent copy of the FSO from operation 405, above.

In operations 475, node N1 or N2 host-side cache can send its version ofthe FSO to storage array.

FIG. 5 illustrates, in block diagram form, a method 500 of file systembuffer cache and host-side cache coherency management in aclustered/distributed file system (C/DFS), managed by a file systemcache coherency logic, in accordance with some embodiments. Structureand logic for implementing method 500 is described above with referenceto FIGS. 2A and 2B.

In operation 505, a first node (N1) in a multi-node file system (MNFS)can receive a “write file system object (FSO),” instruction to write amost recent copy of an FSO, such as FSO 130 of FIG. 2A. The writeoperation may result in the FSO being written to one or more caches, asdistinguished from writing directly to a storage device.

In operation 510, cache coherency logic in, e.g. an operating system120, can send an “invalidate copy of FSO” message to an operating systemof each of a second node (N2) and a third node (N3) to invalidate copiesof the FSO in the buffer cache 125 of each of N2 and N3.

In operation 515, node N2 can invalidate a copy of the FSO in its buffercache, if such a copy of the FSO exists. Similarly, N3 can invalidate acopy of the FSO in its buffer cache, if such as a copy of the FSOexists.

In operation 520, node N2 can invalidate a copy of the FSO in itshost-side buffer cache, if such as copy of the FSO exists. Similarly, N3can invalidate a copy of the FSO in its host-side cache, if such a copyof the FSO exists.

In operation 525, either of N2 or N3 (in this example, N2) can receive a“read FSO” request to read a most recent copy of the FSO. The readrequest asks for the most recent copy of the FSO, and, in an embodiment,the read request does not need to specify a source node, cache, orstorage from where the copy of the FSO is read.

In operation 530, node N2 buffer cache coherency logic can send an“intent to read a most recent copy of FSO” message to N1 and N3 buffercaches.

In operation 535, it can be determined that, in this example, node N1buffer cache has the most recent copy of the FSO, and that node N3 copyof the FSO has been invalidated in operation 515, above.

In operation 540, since the copy of the FSO in the N1 buffer cache isthe most recent copy of the FSO, cache coherency logic in the operatingsystem of node N1 can cause N1 buffer cache to flush the FSO to the N1host-side cache.

In operation 545, cache coherency logic in N1 can flush the copy of theFSO stored in the host-side cache of N1 to the storage device, e.g. astorage array.

In operation 550, cache coherency logic in N1 can notify nodes N2 and N3that the most recent copy of the FSO has been flushed to the storagearray.

In operation 555, cache coherency logic of N1 can optionally receive awrite-acknowledgement from the storage device, e.g. storage array thatthe FSO write to storage is complete.

In operation 560, cache coherency logic of N1 can optionally send thewrite-acknowledgement to nodes N2 and N3 that the FSO has been writtento storage and is available for reading.

In operation 565, cache coherency logic in N2 can cause host-side cacheof N2 to read the FSO from storage.

In operation 570, cache coherency logic in N2 can cause the file buffercache of N2 to read the FSO from host-side cache of N2.

In operation 575, cache coherency logic in N2 can provide the FSO to therequesting application of N2.

FIG. 6 illustrates, in block diagram form, a method 600 of file systembuffer cache and host-side cache coherency management in aclustered/distributed file system (C/DFS), managed by a storage deviceprocessing system, in accordance with some embodiments.

In operation 605, a first node (N1) in a multi-node file system (MNFS)can receive a “write file system object (FSO),” instruction to write amost recent copy of an FSO, such as FSO 130 of FIG. 3A. The writeoperation may result in the FSO being written to one or more caches, asdistinguished from writing directly to a storage device, such as storagearray 250.

In operation 610, cache coherency logic in, e.g. an operating system120, can send an “invalidate copy of FSO” message to an operating system120 of each of a second node (N2) and a third node (N3) to invalidecopies of the FSO in the buffer cache 125 of each of N2 and N3.

In operation 615, node N2 can invalidate a copy of the FSO in its buffercache 125, if such a copy of the FSO exists. Similarly, N3 caninvalidate a copy of the FSO in its buffer cache 125, if such as a copyof the FSO exists.

In operation 620, either of N2 or N3 (in this example, N2) can receive a“read FSO” request to read a most recent copy of the FSO. The readrequest asks for the most recent copy of the FSO, and, in an embodiment,the read request does not need to specify a source node, cache, orstorage from where the copy of the FSO is read.

In operation 625, the read request (1) can be propagated to HSTCoherency Mgt. 270 on storage device 250. In an embodiment, the readrequest can be propagated by OS 120 directly to HST Coherency Mgt. 270on storage array 270, or can be relayed to host-side cache 150 to HSTCoherency Mgt. 270 on storage array 270.

In operation 630, OS 120 cache coherency logic of N1 can send a “flushFSO 130” message to flush their respective buffer caches.

In operation 635, nodes N2 and N3 can flush FSO 130 from buffer cachesof N2 and N3 to their respective host-tier caches. Coherency logic of N1can further flush its own copy of FSO 130 from the N1 buffer cache tothe N1 host-tier cache.

In operation 640, HST Coherency Mgt. 270 on storage device 250 candetermine that the copy of the FSO stored in N1 host-side cache 150 isthe most recent copy of the FSO.

In operation 645, HST Coherency Mgt. 270 can instruct N1 host-side cacheto write its FSO to the storage device, e.g. storage array 250.

In operation 650, N1 host-side cache can write its copy of the FSO tostorage device 250. Since HST Coherency Mgt. 270 forms a part of thestorage device 250, storage device 250 need not send awrite-acknowledgement to N1 host-side cache. In an embodiment, HSTCoherency Mgt. 270 can receive notice of, or detect, completion of thewrite of the FSO to storage device 250.

In operation 655, HST Coherency Mgt. 270 of storage array 250 can sendan “invalidate FSO 130” instruction to the host-side cache 150 of nodesN2 and N3. N1 host-side cache need not be invalidated because itcontained the most recent copy of the FSO in operation 635, above.

In operation 660, HST Coherency Mgt. 270 of storage array 250 caninstruct N2 host-side cache 150 to read the FSO from the storage device250.

In operation 665, N2 buffer cache 125 can read the FSO from N2 host-sidecache 150.

In operation 670, N2 buffer cache can provide the FSO to the requestingN2 Application to fulfill the initial read request of operation 620,above.

In FIG. 7 (“Software Stack”), an exemplary embodiment, applications canmake calls to Services 1 or 2 using several Service APIs and toOperating System (OS) using several OS APIs. Services 1 and 2 can makecalls to OS using several OS APIs.

Note that the Service 2 has two APIs, one of which (Service 2 API 1)receives calls from and returns values to Application 1 and the other(Service 2 API 2) receives calls from and returns values to Application2. Service 1 (which can be, for example, a software library) makes callsto and receives returned values from OS API 1, and Service 2 (which canbe, for example, a software library) makes calls to and receivesreturned values from both as API 1 and OS API 2, Application 2 makescalls to and receives returned values from as API 2.

Note that some or all of the components as shown and described above maybe implemented in software, hardware, or a combination thereof. Forexample, such components can be implemented as software installed andstored in a persistent storage device, which can be loaded and executedin a memory by a processor (not shown) to carry out the processes oroperations described throughout this application. Alternatively, suchcomponents can be implemented as executable code programmed or embeddedinto dedicated hardware such as an integrated circuit (e.g., anapplication specific IC or ASIC), a digital signal processor (DSP), or afield programmable gate array (FPGA), which can be accessed via acorresponding driver and/or operating system from an application.Furthermore, such components can be implemented as specific hardwarelogic in a processor or processor core as part of an instruction setaccessible by a software component via one or more specificinstructions.

FIG. 8 is a block diagram of one embodiment of a computing system 800.The computing system illustrated in FIG. 8 is intended to represent arange of computing systems (either wired or wireless) including, forexample, desktop computer systems, laptop computer systems, cellulartelephones, personal digital assistants (PDAs) includingcellular-enabled PDAs, set top boxes, entertainment systems or otherconsumer electronic devices. Alternative computing systems may includemore, fewer and/or different components. The computing system of FIG. 8may be used to provide a computing device and/or a server device.

Computing system 800 includes bus 805 or other communication device tocommunicate information, and processor 810 coupled to bus 805 that mayprocess information.

While computing system 800 is illustrated with a single processor,computing system 800 may include multiple processors and/orco-processors 810. Computing system 800 further may include randomaccess memory (RAM) or other dynamic storage device 820 (referred to asmain memory), coupled to bus 805 and may store information andinstructions that may be executed by processor(s) 810. Main memory 820may also be used to store temporary variables or other intermediateinformation during execution of instructions by processor 810.

Computing system 800 may also include read only memory (ROM) 830 and/orother static, non-transitory storage device 840 coupled to bus 805 thatmay store static information and instructions for processor(s) 810. Datastorage device 840 may be coupled to bus 805 to store information andinstructions. Data storage device 840 such as flash memory or a magneticdisk or optical disc and corresponding drive may be coupled to computingsystem 800.

Computing system 800 may also be coupled via bus 805 to display device850, such as a light-emitting diode display (LED), touch screen display,or liquid crystal display (LCD), to display information to a user.Computing system 800 can also include an alphanumeric input device 860,including alphanumeric and other keys, which may be coupled to bus 805to communicate information and command selections to processor(s) 810.Another type of user input device is cursor control 865, such as atouchpad, a mouse, a trackball, or cursor direction keys to communicatedirection information and command selections to processor(s) 810 and tocontrol cursor movement on display 850. Computing system 800 may furtherinclude a real-time clock 870. The real-time clock 870 may be used forgenerating date/time stamps for data records, computing elapsed time,and other time-keeping functions. A real-time clock 870 can be abattery-backed chipset with a settable date and time. Alternatively, areal-time clock 870 may include logic to retrieve a real-time from anetwork source such as a server or an Internet server via networkinterfaces 880, described below.

Computing system 800 further may include one or more networkinterface(s) 880 to provide access to a network, such as a local areanetwork. Network interface(s) 880 may include, for example, a wirelessnetwork interface having antenna 885, which may represent one or moreantenna(e). Computing system 800 can include multiple wireless networkinterfaces such as a combination of WiFi, Bluetooth® and cellulartelephony interfaces. Network interface(s) 880 may also include, forexample, a wired network interface to communicate with remote devicesvia network cable 887, which may be, for example, an Ethernet cable, acoaxial cable, a fiber optic cable, a serial cable, or a parallel cable.

In one embodiment, network interface(s) 880 may provide access to alocal area network, for example, by conforming to IEEE 802.11b, 802.11g,or 802.11n standards, and/or the wireless network interface may provideaccess to a personal area network, for example, by conforming toBluetooth® standards. Other wireless network interfaces and/or protocolscan also be supported. In addition to, or instead of, communication viawireless LAN standards, network interface(s) 880 may provide wirelesscommunications using, for example, Time Division, Multiple Access (TDMA)protocols, Global System for Mobile Communications (GSM) protocols, CodeDivision, Multiple Access (CDMA) protocols, and/or any other type ofwireless communications protocol.

In the foregoing specification, the invention has been described withreference to specific embodiments thereof. It will, however, be evidentthat various modifications and changes can be made thereto withoutdeparting from the broader spirit and scope of the invention. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A computer-implemented method for managing cachecoherency of a multi-node file system sharing a storage system, eachnode having a file system buffer cache and a host-side cache,comprising: receiving, by a host-side cache on a first node of themulti-node file system, a copy of a file system object (FSO) from a filesystem buffer cache on the first node; storing the copy of the FSO inthe host-side cache on the first node; sending, by the first node, amessage to a second and a third node to invalidate a copy of the FSO ina host-side cache of each of the second and third nodes in response tothe storing of the copy of the FSO in the host-side cache on the firstnode from the buffer cache on the first node; and sending a copy of theFSO from the host-side cache of the first node to at least the host-sidecache of the second node independently of the shared storage system;wherein each of the first, second, and third nodes comprise host-sidecache coherency logic, and the coherency logic of the host-side cache ofthe first, second, and third nodes communicate with each other toimplement coherency logic for the combined first, second, and third nodehost-side caches.
 2. The method of claim 1, wherein the host-side cachecomprises a non-volatile storage, distinct from the file system buffercache.
 3. The method of claim 1, wherein cache coherency logic of thehost-side cache of the first node is independent of cache coherencylogic of the file system buffer cache of the first node.
 4. The methodof claim 1, wherein the sending of the copy of the FSO from thehost-side cache of the first node to the host-side cache of the secondnode is in response to a request from the second node.
 5. The method ofclaim 1, wherein the copy of the FSO received from the file systembuffer cache of the first node was received in response to a readrequest of an outdated copy of the FSO.
 6. The method of claim 1,further comprising flushing the received copy of the FSO from thehost-side cache of the first node to the storage system in response toan event, wherein the event comprises one of: a receipt of a flushhost-side cache message, the FSO has not been read for a predeterminedperiod of time, storage available in the host-side cache of the firstnode is below a threshold minimum value, or receipt of a request toflush pending writes has been received from the storage system.
 7. Anon-transitory computer-readable medium programmed with executableinstructions that, when executed by a processing system having at leastone hardware processor, perform operations for managing cache coherencyof a multi-node file system sharing a storage system, each node having afile system buffer cache and a host-side cache, comprising: receiving,by a host-side cache on a first node of the multi-node file system, acopy of a file system object (FSO) from a file system buffer cache onthe first node; storing the copy of the FSO in the host-side cache onthe first node; sending, by the first node, a message to a second and athird node to invalidate a copy of the FSO in a host-side cache of eachof the second and third nodes in response to the storing of the copy ofthe FSO in the host-side cache on the first node from the buffer cacheon the first node; and sending a copy of the FSO from the host-sidecache of the first node to at least the host-side cache of the secondnode independently of the shared storage system; wherein each of thefirst, second, and third nodes comprise host-side cache coherency logic,and the coherency logic of the host-side cache of the first, second, andthird nodes communicate with each other to implement coherency logic forthe combined first, second, and third node host-side caches.
 8. Themedium of claim 7, wherein the host-side cache comprises a non-volatilestorage, distinct from the file system buffer cache.
 9. The medium ofclaim 7, wherein cache coherency logic of the host-side cache of thefirst node is independent of cache coherency logic of the file systembuffer cache of the first node.
 10. The medium of claim 7, wherein thesending of the copy of the FSO from the host-side cache of the firstnode to the host-side cache of the second node is in response to arequest from the second node.
 11. The medium of claim 7, wherein thecopy of FSO received from the file system buffer cache of the first nodewas received in response to a read request of an outdated copy of theFSO.
 12. The medium of claim 7, further comprising flushing the receivedcopy of the FSO from the host-side cache of the first node to thestorage system in response to an event, wherein the event comprises oneof: a receipt of a flush host-side cache message, the FSO has not beenread for a predetermined period of time, storage available in thehost-side cache of the first node is below a threshold minimum value, orreceipt of a request to flush pending writes has been received from thestorage system.
 13. A system comprising: a processing system having atleast one hardware processor, the processing system coupled to a memoryprogrammed with executable instructions that, when executed by theprocessing system, perform operations for managing cache coherency of amulti-node file system sharing a storage system, each node having a filesystem buffer cache and a host-side cache, comprising: receiving, by ahost-side cache on a first node of the multi-node file system, a copy ofa file system object (FSO) from a file system buffer cache on the firstnode; storing the copy of the FSO in the host-side cache on the firstnode; sending, by the first node, a message to a second and a third nodeto invalidate a copy of the FSO in a host-side cache of each of thesecond and third nodes in response to the storing of the copy of the FSOin the host-side cache on the first node from the buffer cache on thefirst node; and sending a copy of the FSO from the host-side cache ofthe first node to at least the host-side cache of the second nodeindependently of the shared storage system; wherein each of the first,second, and third nodes comprise host-side cache coherency logic, andthe coherency logic of the host-side cache of the first, second, andthird nodes communicate with each other to implement coherency logic forthe combined first, second, and third node host-side caches.
 14. Thesystem of claim 13, wherein the host-side cache comprises a non-volatilestorage, distinct from the file system buffer cache.
 15. The system ofclaim 13, wherein cache coherency logic of the host-side cache of thefirst node is independent of cache coherency logic of the file systembuffer cache of the first node.
 16. The system of claim 13, wherein thesending of the copy of the FSO from the host-side cache of the firstnode to the host-side cache of the second node is in response to arequest from the second node.
 17. The system of claim 13, wherein thecopy of the FSO received from the file system buffer cache of the firstnode was received in response to a read request of an outdated copy ofthe FSO.
 18. The system of claim 13, further comprising flushing thereceived copy of the FSO from the host-side cache of the first node tothe storage system in response to an event, wherein the event comprisesone of: a receipt of a flush host-side cache message, the FSO has notbeen read for a predetermined period of time, storage available in thehost-side cache of the first node is below a threshold minimum value, orreceipt of a request to flush pending writes has been received from thestorage system.